Skip to content

Conversation

@theobarberbany
Copy link
Contributor

@theobarberbany theobarberbany commented Dec 20, 2023

This adds a CloudConfigTransformer for Azure that will set the VMType to 'standard' if unset.

It also adds the functionality from the cluster-config-operator azure CloudConfigTransformer, as we can no longer rely on it by introducing this transformer.

See #291, OCPBUGS-25483 and OCPBUGS-20213 for more information.

@theobarberbany theobarberbany marked this pull request as draft December 20, 2023 17:16
@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Dec 20, 2023
This adds a CloudConfigTransformer for Azure that will set the VMType to
'standard' if unset.

See openshift#291, OCPBUGS-25483 and OCPBUGS-20213 for more information.
@theobarberbany
Copy link
Contributor Author

/test fmt
/test vet
/test lint
/test images

This change adds the functionality from the cluster-config-operator
azure CloudConfigTransformer.

The functionality we bring over is:

1. Ensure that the Cloud is set in the cloud.conf
   i. If it is set, verify that it is valid and does not conflict with the
      infrastructure config. If it conflicts, we want to error
  ii. If it is not set, default to public cloud (configv1.AzurePublicCloud)

 2. Verify the cloud name set in the infra config is valid, if it is not
 bail with an informative error

See openshift/cluster-config-operator#133 for
the PR that initially added this functionality.
Adds tests for the vmType transformations.
This change stops the tests from segfaulting, as the new config
transformer for Azure expects a PlatformStatus to  be set.
@theobarberbany
Copy link
Contributor Author

/test unit
/test e2e-azure-ovn

@theobarberbany theobarberbany force-pushed the tb/OCPBUGS-25483 branch 2 times, most recently from 1271996 to 6130bfb Compare January 3, 2024 13:07
@theobarberbany
Copy link
Contributor Author

/test unit

@theobarberbany
Copy link
Contributor Author

/retest required

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 3, 2024

@theobarberbany: The /retest command does not accept any targets.
The following commands are available to trigger required jobs:

  • /test e2e-aws-ovn
  • /test e2e-aws-ovn-upgrade
  • /test fmt
  • /test images
  • /test lint
  • /test unit
  • /test vendor
  • /test vet

The following commands are available to trigger optional jobs:

  • /test e2e-alibaba-ovn
  • /test e2e-azure-manual-oidc
  • /test e2e-azure-ovn
  • /test e2e-azure-ovn-upgrade
  • /test e2e-gcp-ovn
  • /test e2e-gcp-ovn-upgrade
  • /test e2e-nutanix-ovn
  • /test e2e-openstack-ovn
  • /test e2e-vsphere-ovn

Use /test all to run the following jobs that were automatically triggered:

  • pull-ci-openshift-cluster-cloud-controller-manager-operator-master-e2e-alibaba-ovn
  • pull-ci-openshift-cluster-cloud-controller-manager-operator-master-e2e-aws-ovn
  • pull-ci-openshift-cluster-cloud-controller-manager-operator-master-e2e-aws-ovn-upgrade
  • pull-ci-openshift-cluster-cloud-controller-manager-operator-master-e2e-azure-ovn
  • pull-ci-openshift-cluster-cloud-controller-manager-operator-master-e2e-azure-ovn-upgrade
  • pull-ci-openshift-cluster-cloud-controller-manager-operator-master-e2e-gcp-ovn
  • pull-ci-openshift-cluster-cloud-controller-manager-operator-master-e2e-gcp-ovn-upgrade
  • pull-ci-openshift-cluster-cloud-controller-manager-operator-master-e2e-openstack-ovn
  • pull-ci-openshift-cluster-cloud-controller-manager-operator-master-e2e-vsphere-ovn
  • pull-ci-openshift-cluster-cloud-controller-manager-operator-master-fmt
  • pull-ci-openshift-cluster-cloud-controller-manager-operator-master-images
  • pull-ci-openshift-cluster-cloud-controller-manager-operator-master-lint
  • pull-ci-openshift-cluster-cloud-controller-manager-operator-master-unit
  • pull-ci-openshift-cluster-cloud-controller-manager-operator-master-vendor
  • pull-ci-openshift-cluster-cloud-controller-manager-operator-master-vet
Details

In response to this:

/retest required

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@theobarberbany
Copy link
Contributor Author

/retest-required

@theobarberbany
Copy link
Contributor Author

/test e2e-azure-ovn
/test e2e-azure-ovn-upgrade

This changes the tests to work with valid JSON as it is now a
requirement of the azure transformer.
@theobarberbany
Copy link
Contributor Author

/retest required
/test e2e-azure-ovn
/test e2e-azure-ovn-upgrade

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 3, 2024

@theobarberbany: The /retest command does not accept any targets.
The following commands are available to trigger required jobs:

  • /test e2e-aws-ovn
  • /test e2e-aws-ovn-upgrade
  • /test fmt
  • /test images
  • /test lint
  • /test unit
  • /test vendor
  • /test vet

The following commands are available to trigger optional jobs:

  • /test e2e-alibaba-ovn
  • /test e2e-azure-manual-oidc
  • /test e2e-azure-ovn
  • /test e2e-azure-ovn-upgrade
  • /test e2e-gcp-ovn
  • /test e2e-gcp-ovn-upgrade
  • /test e2e-nutanix-ovn
  • /test e2e-openstack-ovn
  • /test e2e-vsphere-ovn

Use /test all to run the following jobs that were automatically triggered:

  • pull-ci-openshift-cluster-cloud-controller-manager-operator-master-e2e-alibaba-ovn
  • pull-ci-openshift-cluster-cloud-controller-manager-operator-master-e2e-aws-ovn
  • pull-ci-openshift-cluster-cloud-controller-manager-operator-master-e2e-aws-ovn-upgrade
  • pull-ci-openshift-cluster-cloud-controller-manager-operator-master-e2e-azure-ovn
  • pull-ci-openshift-cluster-cloud-controller-manager-operator-master-e2e-azure-ovn-upgrade
  • pull-ci-openshift-cluster-cloud-controller-manager-operator-master-e2e-gcp-ovn
  • pull-ci-openshift-cluster-cloud-controller-manager-operator-master-e2e-gcp-ovn-upgrade
  • pull-ci-openshift-cluster-cloud-controller-manager-operator-master-e2e-openstack-ovn
  • pull-ci-openshift-cluster-cloud-controller-manager-operator-master-e2e-vsphere-ovn
  • pull-ci-openshift-cluster-cloud-controller-manager-operator-master-fmt
  • pull-ci-openshift-cluster-cloud-controller-manager-operator-master-images
  • pull-ci-openshift-cluster-cloud-controller-manager-operator-master-lint
  • pull-ci-openshift-cluster-cloud-controller-manager-operator-master-unit
  • pull-ci-openshift-cluster-cloud-controller-manager-operator-master-vendor
  • pull-ci-openshift-cluster-cloud-controller-manager-operator-master-vet
Details

In response to this:

/retest required
/test e2e-azure-ovn
/test e2e-azure-ovn-upgrade

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@theobarberbany
Copy link
Contributor Author

/retest-required

@theobarberbany
Copy link
Contributor Author

/test e2e-azure-ovn
/test e2e-azure-ovn-upgrade

@theobarberbany
Copy link
Contributor Author

/retest

@theobarberbany
Copy link
Contributor Author

/test unit

@theobarberbany
Copy link
Contributor Author

/test e2e-azure-ovn-upgrade
/test e2e-aws-ovn-upgrade

@JoelSpeed
Copy link
Contributor

/approve
/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jan 4, 2024
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 4, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: JoelSpeed

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 4, 2024
@theobarberbany theobarberbany changed the title Adds CloudConfigTransformer for Azure OCPBUGS-25483: Adds CloudConfigTransformer for Azure Jan 4, 2024
@openshift-ci-robot openshift-ci-robot added jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. labels Jan 4, 2024
@openshift-ci-robot
Copy link

@theobarberbany: This pull request references Jira Issue OCPBUGS-25483, which is invalid:

  • expected the bug to target the "4.16.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

This adds a CloudConfigTransformer for Azure that will set the VMType to 'standard' if unset.

It also adds the functionality from the cluster-config-operator azure CloudConfigTransformer, as we can no longer rely on it by introducing this transformer.

See #291, OCPBUGS-25483 and OCPBUGS-20213 for more information.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot openshift-ci-robot added the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Jan 4, 2024
@theobarberbany
Copy link
Contributor Author

/jira refresh

@openshift-ci-robot
Copy link

@theobarberbany: This pull request references Jira Issue OCPBUGS-25483, which is invalid:

  • expected the bug to target the "4.16.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@theobarberbany
Copy link
Contributor Author

/jira refresh

@openshift-ci-robot
Copy link

@theobarberbany: This pull request references Jira Issue OCPBUGS-25483, which is invalid:

  • expected the bug to target the "4.16.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@theobarberbany
Copy link
Contributor Author

/jira refresh

@openshift-ci-robot openshift-ci-robot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Jan 4, 2024
@openshift-ci-robot
Copy link

@theobarberbany: This pull request references Jira Issue OCPBUGS-25483, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.16.0) matches configured target version for branch (4.16.0)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @sunzhaohua2

Details

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot openshift-ci-robot removed the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Jan 4, 2024
@openshift-ci openshift-ci bot requested a review from sunzhaohua2 January 4, 2024 18:04
@theobarberbany
Copy link
Contributor Author

/retest-required

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 4, 2024

@theobarberbany: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/e2e-azure-ovn-upgrade cf0220e link unknown /test e2e-azure-ovn-upgrade
ci/prow/e2e-alibaba-ovn cf0220e link false /test e2e-alibaba-ovn
ci/prow/e2e-vsphere-ovn cf0220e link false /test e2e-vsphere-ovn
ci/prow/e2e-openstack-ovn cf0220e link false /test e2e-openstack-ovn

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@openshift-merge-bot openshift-merge-bot bot merged commit ca380e9 into openshift:master Jan 4, 2024
@openshift-ci-robot
Copy link

@theobarberbany: Jira Issue OCPBUGS-25483: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-25483 has been moved to the MODIFIED state.

Details

In response to this:

This adds a CloudConfigTransformer for Azure that will set the VMType to 'standard' if unset.

It also adds the functionality from the cluster-config-operator azure CloudConfigTransformer, as we can no longer rely on it by introducing this transformer.

See #291, OCPBUGS-25483 and OCPBUGS-20213 for more information.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-bot
Copy link

[ART PR BUILD NOTIFIER]

This PR has been included in build ose-cluster-cloud-controller-manager-operator-container-v4.16.0-202401042211.p0.gca380e9.assembly.stream for distgit ose-cluster-cloud-controller-manager-operator.
All builds following this will include this PR.

@sdodson
Copy link
Member

sdodson commented Jan 5, 2024

/cherry-pick release-4.15

@openshift-cherrypick-robot

@sdodson: new pull request created: #317

Details

In response to this:

/cherry-pick release-4.15

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants